Payment request types
The payment request type is set on the type parameter on the call to, for example, the createPaymentRequest method.
These are the supported types:
|
Payment request type |
Use this when... |
Description |
|---|---|---|
|
payment |
purchased goods or services are not delivered immediately |
A successful payment request is created with <TransactionStatus> set to preauth. You must then capture the payment using the captureReservation method, or using the Merchant Information Interface. payment is automatically be changed to paymentAndCapture if the payment method does not support reservations.
|
|
paymentAndCapture |
purchased goods or services are delivered immediately |
The payment is authorized and captured immediately. In some countries it is illegal to capture the payment before sending the physical goods.
|
|
verifyCard |
You are only verifying that a credit card is valid, but no money is reserved or captured. If the verification is successful, a transaction is created with TransactionStatus set to card_verified. Not all credit card acquirers support verifyCard. For more information about different providers, see Payment methods and providers. If the credit card issuer doesn’t support zero authorisation transactions, your customer will see, for example, a 1 EUR authorisation on their account. |
|
|
credit |
You are crediting your customer. Not all payment acquirers support this. For more information about different providers, see Payment methods and providers. |
You can also set up different subscription types. For more information, see Set up a subscription.
|
Payment request type |
Description |
|---|---|
|
subscription |
The payment is part of a subscription. The subscription is set up, and the payment is authorized immediately, but as a merchant, you have to capture each instalment separately using the captureReservation or chargeSubscription method, or using the Merchant Information Interface. |
|
subscriptionAndCharge |
The subscription is set up, and an attempt is made to capture the first instalment payment. The XML response has two <Transaction> elements. If either the subscription setup or the capture is successful, the <Result> XML response parameter is set to Success, even if the other transaction fails. This means that you cannot rely solely on the <Result> parameter to determine whether the transaction was successful.
|
|
subscriptionAndReserve |
The subscription is set up, and an attempt is made to reserve the first instalment payment. Not all acquirers support this. For more information, see Payment methods and providers.
If either the subscription setup, or the reservation is successful, the <Result> XML response parameter is set to Success, even if one of the transactions fail. The XML response has two <Transaction> elements. This means that you cannot rely solely on the <Result> parameter to determine whether the transaction was successful. |